Minutes, IBIS Quality Committee 05 January 2010 11-12 AM EST (8-9 AM PST) ROLL CALL Adam Tambone Anders Ekholm, Ericsson Barry Katz, SiSoft Benny Lazer Benjamin P Silva Bob Cox, Micron * Bob Ross, Teraspeed Consulting Group Brian Arsenault David Banas, Xilinx Eckhard Lenski, Nokia Siemens Networks Eric Brock Guan Tao, Huawei Technologies Gregory R Edlund Hazem Hegazy Huang Chunxing, Huawei Technologies John Figueroa John Angulo, Mentor Graphics Katja Koller, Nokia Siemens Networks Kevin Fisher Kim Helliwell, LSI Logic Lance Wang, IOMethodology Lijun, Huawei Lynne Green, Green Streak Programs * Mike LaBonte, Cisco Systems Mike Mayer, SiSoft * Moshiul Haque, Micron Technology Muniswarareddy Vorugu, ARM Ltd * Pavani Jella, TI Peter LaFlamme Randy Wolff, Micron Technology Radovan Vuletic, Qimonda Robert Haller, Enterasys Roy Leventhal, Leventhal Design & Communications Sherif Hammad, Mentor Graphics Tim Coyle, Signal Consulting Group Todd Westerhoff, SiSoft Tom Dagostino, Teraspeed Consulting Group Kazuyoshi Shoji, Hitachi Sadahiro Nonoyama Everyone in attendance marked by * NOTE: "AR" = Action Required. -----------------------MINUTES --------------------------- Mike LaBonte conducted the meeting. Call for opens and patent disclosures: - No one declared a patent. - Mike has election duties Jan 19, no meeting AR Review: - Moshiul rework IQ checklist for IQ 2.0 - Done. Reviewed today New items: Mike showed Moshiul's new IQ checklist spreadsheet: - Bob: We should add Notes and Cautions on sheet 1 - Moshiul: The 2.1 check is also in the component tab - Mike: We decided that 2.1 is a top level check - There must be one component tab for each [Component] - Mike: The default status should not be PASS - Pavani: A dash is a common symbol for "N/A" - Mike: An Excel macro could set IQ Level automatically - The first page couldn't have one because it doesn't know which tabs exist - Bob: It could enforce rules for correlation Moshiul showed the example checklist: - Moshiul: Added summary rows for each component and model - It has comments about exceptions - Package checks are NA because it is a bare die - Moshiul: Should lack of D_overshoot be an exception or NA? - Mike: That is a relaxation of S_overshoot - We can't make vendors specify it - In that case it is NA - Bob: We can only document what is specified - These are fundamental questions - Mike: Comment "Not Available" for NA is redundant - It could be "Not in datasheet" - Bob: We could reference JEDEC specs in a comment - Bob: This is a nice format - It highlights the things to look for - Moshiul: We have lots of models that have the same data - Some tabs could cover a range of similar models - Mike: As long as all models are actually checked - Bob: It might help if there are many models - It's important to give information whether a model passes or fails - Mike: Should row 1 of model tabs have "MODELS(S)"? - The same applies to components - Bob: It would PASS only if they all PASS Mike: It would be nice to have a spreadsheet tool for IBIS models - It would have models across columns, parameters by rows - Bob: Zuken had a free tool like that - Moshiul: It's called IBISinfo Mike showed the IQ Checklist web page: - The new checklist will be posted to the website after Moshiul updates it - Mike: It really helps to have both the template and an example - Currently there is also an example IBIS file on the web page - That may be slightly helpful, to show the relation of data to checks - Moshiul: It may be possible to provide that Meeting ended at 12:10 PM Eastern Time.